P2P Continuous Controls Monitoring Demo

⚡

Procure-to-Pay CCM Sandbox

Continuous Controls Monitoring (CCM) detects compliance violations, manual overrides, and transaction anomalies deterministically in the browser. Plant mock audit test cases, run detection, and see how Claude Haiku generates natural language audit narratives.

What is this configuration for?

Use this panel to calibrate control limits and test coverage. Planting cases verifies that detection rules run accurately (perfect match in reconciliation stats), and demonstrates AI narrative summaries and ledger drills.

Scenario Configurator

v1.0.0

Baseline Ledger Size

Generates a clean baseline ledger where 100% of transactions adhere to normal compliance rules (0 false positives).

Total Transactions 0 Clean base + injected cases

Flagged Exceptions 0 Deterministic exceptions detected

Clean Transactions 0 Adhering strictly to standard checks

Reconciliation Rate 0/0 Planted cases vs detected matches

Control Reconciliation Table

Audit Control Rule	Planted	Detected	Match

Exception Volume by Control Rule

T1 = Split POs · T2 = Round Invoices · T3 = Out-of-Hours · T4 = SoD · T5 = Exact Duplicates · T6 = Fuzzy Duplicates · T7 = Broken 3-Way · T8 = Non-Master · T9 = Bank Change · T10 = Sequential

CCM Methodology Legend & Rule Guide

▼ Expand Guide

Continuous Controls Monitoring (CCM) Rule Definitions

T1 Split POs: ≥ 3 transactions for same vendor in 7 days, each under the $10,000 limit but summing to ≥ $10,000.

T2 Round Invoices: Invoice amount has a round integer value (multiples of $5k) and is ≥ $5,000.

T3 Out-of-Hours: Transactions approved during weekends (Sat/Sun) or late night hours (18:00 to 07:59).

T4 Segregation of Duties: Invoices approved by the exact same user ID that raised the Purchase Order (PO).

T5 Exact Duplicates: Same vendor ID + same amount + same invoice number (identifies double processing).

T6 Fuzzy Duplicates: Same vendor + amount within ±3 days OR invoice numbers differing by exactly 1 character.

T7 Broken 3-Way Match: Invoices processed directly for payment without a valid PO reference number.

T8 Non-Master Vendor: Payments issued to vendor IDs not registered in the approved Vendor Master Directory.

T9 Bank Detail Change: Invoice paid to account numbers differing from the Master registered routing info.

T10 Sequential Invoices: ≥ 3 sequential invoice IDs from same vendor in close dates (potential invoice splitting).

* Note: For Split POs (T1) and Sequential Invoices (T10), multiple separate cases might merge into a single audit exception if their transaction dates happen to fall in the same rolling windows. This explains why "cases detected" can sometimes be lower than "cases planted", simulating realistic cluster consolidation.

Data Provenance Legend

Deterministic (CCA Engine): All stats cards, charts, exception counts, and flag highlights are calculated locally using strict deterministic logic.

Generative AI (Claude LLM): The LLM is only utilized as a summarization layer to write the executive overview and narrate findings.

Transaction Ledger

Show:

Showing 0 of 0 records

Txn ID	Date & Time	Vendor Name	Invoice No	PO Reference	Amount	Approver	Bank Account	Control Flags